R Notebook

# load necessary packages
library(tidyverse)
library(mosaic)
library(DataComputing)
library(ggplot2)

Guiding Question

What factors are common between all hall of fame MLB baseball players?

Purpose

This document is required to indicate where various requirements can be found within your Final Project Report Rmd. You must indicate line numbers as they appear in your final Rmd document accompanying each of the following required tasks. Points will be deducted if line numbers are missing or differ signficantly from the submitted Final Rmd document.

Final Project Requirements

Data Access

Description: (1) Analysis includes at least two different data sources. (2) Primary data source may NOT be loaded from an R package–though supporting data may. (3) Access to all data sources is contained within the analysis. (4) Imported data is inspected at beginning of analysis using one or more R functions: e.g., str, glimpse, head, tail, names, nrow, etc

1. .Rmd Line numbers where at least two different data sources are imported:

HallOfFame <- read_csv("core/HallOfFame.csv")

Parsed with column specification:
cols(
  playerID = col_character(),
  yearID = col_double(),
  votedBy = col_character(),
  ballots = col_double(),
  needed = col_double(),
  votes = col_double(),
  inducted = col_character(),
  category = col_character(),
  needed_note = col_character()
)

AllstarFull <- read_csv("core/AllstarFull.csv")

Parsed with column specification:
cols(
  playerID = col_character(),
  yearID = col_double(),
  gameNum = col_double(),
  gameID = col_character(),
  teamID = col_character(),
  lgID = col_character(),
  GP = col_double(),
  startingPos = col_double()
)

Salaries <- read_csv("core/Salaries.csv")

Parsed with column specification:
cols(
  yearID = col_double(),
  teamID = col_character(),
  lgID = col_character(),
  playerID = col_character(),
  salary = col_double()
)

Batting <- read_csv("core/Batting.csv")

Parsed with column specification:
cols(
  .default = col_double(),
  playerID = col_character(),
  teamID = col_character(),
  lgID = col_character(),
  IBB = col_logical(),
  HBP = col_logical(),
  SH = col_logical(),
  SF = col_logical()
)
See spec(...) for full column specifications.
87292 parsing failures.
 row col           expected actual               file
1999 HBP 1/0/T/F/TRUE/FALSE      2 'core/Batting.csv'
2001 HBP 1/0/T/F/TRUE/FALSE      2 'core/Batting.csv'
2020 HBP 1/0/T/F/TRUE/FALSE      2 'core/Batting.csv'
2022 HBP 1/0/T/F/TRUE/FALSE      2 'core/Batting.csv'
2027 HBP 1/0/T/F/TRUE/FALSE      5 'core/Batting.csv'
.... ... .................. ...... ..................
See problems(...) for more details.

2. .Rmd Line numbers for inspecting data intake:

head(HallOfFame)

glimpse(HallOfFame)

Observations: 4,191
Variables: 9
$ playerID    <chr> "cobbty01", "ruthba01", "wagneho01", "mathech01", "johnswa01", "lajoina01", "speaktr01", "youngcy01", "hornsro01", "coch…
$ yearID      <dbl> 1936, 1936, 1936, 1936, 1936, 1936, 1936, 1936, 1936, 1936, 1936, 1936, 1936, 1936, 1936, 1936, 1936, 1936, 1936, 1936, …
$ votedBy     <chr> "BBWAA", "BBWAA", "BBWAA", "BBWAA", "BBWAA", "BBWAA", "BBWAA", "BBWAA", "BBWAA", "BBWAA", "BBWAA", "BBWAA", "BBWAA", "BB…
$ ballots     <dbl> 226, 226, 226, 226, 226, 226, 226, 226, 226, 226, 226, 226, 226, 226, 226, 226, 226, 78, 78, 78, 226, 78, 78, 226, 226, …
$ needed      <dbl> 170, 170, 170, 170, 170, 170, 170, 170, 170, 170, 170, 170, 170, 170, 170, 170, 170, 59, 59, 59, 170, 59, 59, 170, 170, …
$ votes       <dbl> 222, 215, 215, 205, 189, 146, 133, 111, 105, 80, 77, 60, 58, 55, 51, 47, 40, 39, 39, 33, 33, 32, 21, 21, 20, 17, 17, 16,…
$ inducted    <chr> "Y", "Y", "Y", "Y", "Y", "N", "N", "N", "N", "N", "N", "N", "N", "N", "N", "N", "N", "N", "N", "N", "N", "N", "N", "N", …
$ category    <chr> "Player", "Player", "Player", "Player", "Player", "Player", "Player", "Player", "Player", "Player", "Player", "Player", …
$ needed_note <chr> NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, …

head(Salaries)

glimpse(Salaries)

Observations: 26,428
Variables: 5
$ yearID   <dbl> 1985, 1985, 1985, 1985, 1985, 1985, 1985, 1985, 1985, 1985, 1985, 1985, 1985, 1985, 1985, 1985, 1985, 1985, 1985, 1985, 198…
$ teamID   <chr> "ATL", "ATL", "ATL", "ATL", "ATL", "ATL", "ATL", "ATL", "ATL", "ATL", "ATL", "ATL", "ATL", "ATL", "ATL", "ATL", "ATL", "ATL…
$ lgID     <chr> "NL", "NL", "NL", "NL", "NL", "NL", "NL", "NL", "NL", "NL", "NL", "NL", "NL", "NL", "NL", "NL", "NL", "NL", "NL", "NL", "NL…
$ playerID <chr> "barkele01", "bedrost01", "benedbr01", "campri01", "ceronri01", "chambch01", "dedmoje01", "forstte01", "garbege01", "harpet…
$ salary   <dbl> 870000, 550000, 545000, 633333, 625000, 800000, 150000, 483333, 772000, 250000, 1500000, 455000, 407500, 275000, 775000, 16…

Data Wrangling (5 out of 8 required)

Description: Students need not use every function and method introduced in STAT 184, but clear demonstration of proficiency should include proper use of 5 out of the following 8 topics from class: (+) various data verbs for general data wrangling like filter, mutate, summarise, arrange, group_by, etc. (+) joins for multiple data tables. (+) spread & gather to stack/unstack variables (+) regular expressions (+) reduction and/or transformation functions like mean, sum, max, min, n(), rank, pmin, etc. (+) user-defined functions (+) loops and control flow (+) machine learning

1. .Rmd Line number(s) for general data wrangling:

InductedP<-
  HallOfFame%>%
  filter(inducted == "Y")%>%
  select(playerID, yearID)
InductedP

Money<-
  Salaries%>%
  select(teamID, playerID, salary)
Money

2. .Rmd Line number(s) for a join operation:

HallMoney<-
  InductedP%>%
  inner_join(Money, by = c("playerID" = "playerID"))
HallMoney

WholeLeague <-
  Batting %>%
  filter(G > 20)%>%
  select(playerID, yearID)
WholeLeague

  
WLeagueS<-
  WholeLeague%>%
  inner_join(Money, by =c("playerID" = "playerID"))
WLeagueS

This join operation will join the HallOfFame table with the AllstarFull table to help us find the correlation between the players that made the Hall Of Fame and played in All Star Games. We can use this joined data set to figure out commonalities between all of the Hall Of Fame baseball players.

# Join the AllstarFull table with the HallOfFame table
AllStarHallOfFameJoin <-
  AllstarFull %>%
  inner_join(HallOfFame, by = c("playerID" = "playerID"))
# Use data wrangling to alter the table to find the amount of times an inducted players played in All Star Games
AllStarHallOfFameTable <-
  AllStarHallOfFameJoin %>%
  filter(inducted == "Y") %>%
  group_by(playerID, inducted) %>%
  summarise(AppearanceCount = n()) %>%
  arrange(desc(AppearanceCount))
  
AllStarHallOfFameTable

#Batting stats
BattingAndHallofFame <- 
  Batting %>%
  full_join(HallOfFame, by = c("playerID" = "playerID")) %>%
  filter(inducted == "Y")
#Only Take stats with players having more than 20 games
BattingAndHallofFame <-
  BattingAndHallofFame %>%
    filter(G > 20) 
HallOfFamerHomies <-
  BattingAndHallofFame %>%
    summarise(AvgHomeRunsPerPlayerHOF = mean(H))
EverybodyBatting <-
  Batting %>%
    filter(G > 20) %>%
    summarise(AvgHomeRunPerPlayerEverybody = mean(H))
HallOfFamerHomies

EverybodyBatting

#Which league has greater HOF chance
LeagueFromAmerican <-
  BattingAndHallofFame %>%
    filter(lgID == "AA") %>%
    summarise(TotalFromAmerican = n())
LeagueFromNational <-
  BattingAndHallofFame %>%
    filter(lgID == "NL") %>%
    summarise(TotalFromNational = n())
LeagueFromAmerican

LeagueFromNational

3. .Rmd Line number(s) for a spread or gather operation (or equivalent):

4. .Rmd Line number(s) for use of regular expressions:

5. .Rmd Line number(s) for use of reduction and/or transformation functions:

6. .Rmd Line number(s) for use of user-defined functions:

7. .Rmd Line number(s) for use of loops and/or control flow:

8. .Rmd Line number(s) for use of machine learning (not “wrangling” but scored here):

Data Visualization (3 of 5 required)

Description: Students need not use every function and method introduced in STAT 184, but clear demonstration of proficiency should include a range of useful of data visualizations that are (1) relevant to stated research question for the analysis, (2) include at least one effective display of many–at least 3–variables, and (3) include 3 of the following 5 visualization techniques learned in STAT 184: (+) use of multiple geoms such as points, density, lines, segments, boxplots, bar charts, histograms, etc (+) use of multiple aesthetics–not necessarily all in the same graph–such as color, size, shape, x/y position, facets, etc (+) layered graphics such as points and accompanying smoother, points and accompanying boxplots, overlaid density distributions, etc (+) leaflet maps (+) decision tree and/or dendogram displaying machine learning model results

1. .Rmd Line number(s) for use of mulitple different geoms:

HallMoney%>%
ggplot(aes(x = playerID, y = salary))+
  geom_point()

2. .Rmd Line number(s) for use of multiple aesthetics:

3. .Rmd Line number(s) for use of layered graphics:

4. .Rmd Line number(s) for use of leaflet maps:

5. .Rmd Line number(s) for use of decision tree or dendogram results:

Other requirements (Nothing for you to report in this Guidance Document)

1. All data visualizations must be relevant to the stated research question, and the report must include at least one effective display of many–at least 3–variables

2. Code quality: Code formatting is consistent with Style Guide Appendix of DataComputing eBook. Specifically, all code chunks demonstrate proficiency with (1) meaningful object names (2) proper use of white space especially with respect to infix operators, chain operators, commas, brackets/parens, etc (3) use of <- assignment operator throughout (4) use of meaningful comments.

3. Narrative quality: The narrative text (1) clearly states one research question that motivates the overall analysis, (2) explains reasoning for each significant step in the analysis and it’s relationship to the research question, (3) explains significant findings and conclusions as they relate to the research question, and (4) is completely free of errors in spelling and grammar

4. Overall Quality: Submitted project shows significant effort to produce a high-quality and thoughtful analysis that showcases STAT 184 skills. (2) The project must be self-contained, such that the analysis can be entirely rerun without errors. (3) Analysis is coherent, well-organized, and free of extraneous content such as data dumps, unrelated graphs, and other content that is not overtly connected to the research question.

5. EXTRA CREDIT (1) Project is submitted as a self-contained GitHub Repo (2) project submission is a functioning github.io webpage generated for the project Repo. Note: a link to the GitHub Repo itself will be awarded partial credit, but does not itself qualify as a “webpage” of the analysis.